Methods and apparatus to trigger maintenance and upgrades of access networks

ABSTRACT

Example methods and apparatus to trigger maintenance and upgrades of access networks are disclosed. An example method comprises obtaining a first value representing a number of unassigned ports associated with a first digital subscriber line access multiplexer (DSLAM), obtaining a second value representing a projected number of ports associated with the first DSLAM needed to satisfy at least one of anticipated, projected or pending service requests, and determining whether to automatically submit a preventative maintenance trouble ticket for the first DSLAM based on the first and second values.

CROSS REFERENCE TO RELATED APPLICATION

This patent is a continuation and claims priority to U.S. applicationSer. No. 12/334,194, filed Dec. 12, 2008, entitled “Methods andApparatus to Trigger Maintenance and Upgrades of Access Networks,” whichis hereby incorporated herein by referenced in its entirety.

FIELD OF DISCLOSURE

This disclosure relates generally to access networks and, moreparticularly, to methods and apparatus to trigger maintenance andupgrades of access networks.

BACKGROUND

Access networks and/or systems using digital subscriber line (DSL)technologies are commonly utilized to provide communication services tocustomer premises. DSL technologies enable service providers to utilizetelephone lines to connect customers to, for example, a high data-ratebroadband Internet network, a broadband service and/or broadbandcontent. An example telephone line uses twisted-pair copper wire toprovide Plain Old Telephone System (POTS) services. A communicationcompany and/or service provider may utilize a plurality of DSL modemsimplemented by a DSLAM and/or a video ready access device (VRAD) at acentral office (CO), a remote terminal (RT) or a serving area interface(SAI) to provide DSL communication services to a plurality ofcustomer-premises DSL modems located at respective customer premises. Ingeneral, a DSLAM/VRAD receives broadband service content for asubscriber from, for example, a backbone server. A CO DSL modem at theDSLAM/VRAD forms from the content a downstream DSL signal to betransmitted to a customer-premises DSL modem via a telephone line thatelectrically couples the CO DSL modem at the SAI, RT or CO to thecustomer-premises DSL modem. Likewise, the CO DSL modem receives anupstream DSL signal from the customer-premises DSL modem via thecorresponding subscriber's telephone line, and the DSLAM/VRAD providesthe data received via the upstream DSL signal to the backbone server.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of an example access networkconstructed in accordance with the teachings of this disclosure.

FIG. 2 illustrates an example maintenance report that may be generatedby the example availability analyzer of the FIG. 1.

FIG. 3 illustrates an example capacity-planning report that may begenerated by the example availability analyzer of FIG. 1.

FIG. 4 illustrates an example manner of implementing the exampleavailability analyzer of FIG. 1.

FIGS. 5A and 5B are collectively a flowchart representative of anexample process that may be carried out to implement the exampleavailability analyzers of FIGS. 1 and 4.

FIG. 6 is a schematic illustration of an example processor platform thatmay be used and/or programmed to carry out the example process of FIGS.5A and 5B, and/or to implement any or all of the methods and apparatusdisclosed herein.

DETAILED DESCRIPTION

Example methods and apparatus to trigger maintenance and upgrades ofaccess networks are disclosed. A disclosed example method includesobtaining a first value representing a number of unassigned portsassociated with a first digital subscriber line (DSL) access multiplexer(DSLAM), obtaining a second value representing a projected number ofports associated with the first DSLAM needed to satisfy at least one ofanticipated, projected or pending service requests, and determiningwhether to automatically submit a preventative maintenance troubleticket for the first DSLAM based on the first and second values.

A disclosed example apparatus includes a trouble ticket system, a loopfacility assignment and control system (LFACS), a capacity-planningserver and an availability analyzer. The LFACS is to provide a firstvalue representing a number of unassigned ports associated with a firstDSLAM. The capacity-planning server is to provide a second valuerepresenting a projected number of ports associated with the first DSLAMneeded to satisfy at least one of anticipated, projected or pendingservice requests. The availability analyzer is to compare a first ratioof the first and second values to a first threshold to determine whetherto automatically submit a maintenance trouble ticket for the first DSLAMto the trouble ticket system, the submitted trouble ticket identifyingthat one or more bad ports associated with the first DSLAM are to beinvestigated.

In the interest of brevity and clarity, throughout the followingdisclosure references will be made to an example access network 100 ofFIG. 1. However, the methods and apparatus described herein to triggermaintenance and upgrades of access networks are applicable to othertypes of access networks and/or communication systems constructed usingother network technologies, topologies and/or protocols. Other examplesystems include, but are not limited to, those associated with publicswitched telephone network (PSTN) systems, public land mobile network(PLMN) systems (e.g., cellular), wireless distribution systems, wired orcable distribution systems, coaxial cable distribution systems, UltraHigh Frequency (UHF)/Very High Frequency (VHF) radio frequency systems,satellite or other extra-terrestrial systems, cellular distributionsystems, power-line broadcast systems, fiber optic networks, passiveoptical network (PON) systems, and/or any combination and/or hybrid ofthese devices, systems and/or networks.

FIG. 1 illustrates the example access network 100. The example accessnetwork 100 of FIG. 1 includes any number and/or type(s) of centraloffices (COs), one of which is designated at reference numeral 105,remote terminals (RTs) and/or serving area interfaces (SAIs). Theexample CO 105 of FIG. 1, and/or other COs, RTs and/or SAIs are used toprovide data and/or communication services to one or more customerpremises, three of which are designated at reference numerals 110, 111and 112. Example data and/or communication services include, but are notlimited to, telephone services, Internet services, data services,messaging services, instant messaging services, electronic mail (email)services, chat services, video services, audio services, gamingservices. To provide DSL communication services to the customer premises110-112, the example CO 105 of FIG. 1 includes any number and/or type(s)of DSLAMs and/or video-ready access devices (VRADs), three of which aredesignated at reference numerals 115, 116 and 117, and the examplecustomer premises 110-112 include any type(s) of customer-premisesequipment (CPE) DSL modems 120, 121 and 122. The example DSLAMs/VRADs115-117 of FIG. 1 include and/or implement one or more CO DSL modems(not shown) for respective ones of the customer premises 110-112. CO DSLmodems are sometimes referred to in the industry as “DSLAM ports,” “VRADports,” or simply “ports.” The example DSLAMs/VRADs 115-117, the CO DSLmodems within the DSLAMs/VRADs 115-117, and/or the example CPE DSLmodems 120-122 of FIG. 1 may be implemented, for example, in accordancewith the International Telecommunications Union—TelecommunicationsSector (ITU-T) G.993.x family of standards for very high-speed DSL(VDSL), and/or the ITU-T G.992.x family of standards for asymmetric DSL(ADSL). However, the CO DSL modems and/or the CPE DSL modems 120-122 maybe implemented in accordance with any past, present and/or futurestandard, specification and/or recommendation.

While in the illustrated example of FIG. 1, the DSLAMs/VRADs 115-117 areimplemented at the CO 105, any of the DSLAMs/VRADs 115-117 may be,additionally or alternatively, implemented at an RT, at an SAI and/or atany other location between the CO 105 and the customer premises 110-112.In such instances, a fiber-optic cable (not shown) may be used, forexample, to communicatively couple the remotely located DSLAM/VRAD115-117 to the CO 105.

In the illustrated example of FIG. 1, the DSLAM 115 provides DSLservices to the CPE DSL modems 120-122 via respective subscriber lines125, 126 and 127. Subscriber lines are sometimes also referred to in theindustry as “wire-pairs”, “subscriber loops” and/or “loops.” Whilethroughout this disclosure reference is made to the example loops125-127 of FIG. 1, a loop (e.g., any of the example loops 125-127) usedto provide a DSL service to a customer-premises location (e.g., any ofthe locations 110-112) may include and/or be constructed from one ormore segments of twisted-pair telephone wire (e.g., any combination of afeeder one (F1) cable, a feeder two (F2) cable, a feeder three (F3)cable, a feeder four (F4) cable, a distribution cable, a drop cable,and/or customer-premises wiring), terminals, and/or distributions points(e.g., an RT, an SAI, a serving terminal, a vault, a pedestal and/or anyother type(s) of wiring distribution points). Such segments oftwisted-pair telephone wire may be spliced and/or connected end-to-end,and/or may be connected at only one end, thereby creating one or morebridged-taps. Regardless of the number, type(s), gauge(s) and/ortopology of twisted-pair telephone wires used to construct the exampleloops 125-127, they will be referred to herein in the singular form, butit will be understood that the term “loop” may refer to one or moretwisted-pair telephone wire segments and may include one or more bridgedtaps.

To assign DSLAM/VRAD ports to the example loops 125-127, the exampleaccess network 100 of FIG. 1 includes any type of mechanized loopassignment center (MLAC) 130, any type of LFACS 135 and a port/loopassignment database 140. DSLAM/VRAD port to loop assignments may bestored in the example port/loop assignment database 140 of FIG. 1 usingany number and/or type(s) of data structures. The example port/loopassignment database 140 may be stored in any number and/or type(s) ofvolatile and/or non-volatile memory(-ies) and/or memory device(s) (notshown).

In response to, for example, an order for new DSL service for aparticular customer premises 110-112 received from, for example, anytype of customer service server 145, the example MLAC 130 of FIG. 1assigns and/or selects a particular port of a DSLAM/VRAD 115-117 to beused to provide the DSL service to that customer premises 110-112. Theexample customer service server 145 of FIG. 1 may interact with theexample MLAC 130 using any number and/or type(s) of method(s),application programming interface(s) (API(s)) and/or logic. When thepresently considered customer premises 110-112 is already associatedwith a particular loop (e.g., any of the example loops 125-127) toreceive, for example, plain old telephone service (POTS), the exampleMLAC 130 associates the already associated loop with the selectedDSLAM/VRAD port. When the presently considered customer premises 115-117is not already associated with a loop 125-127, the MLAC 130 selects aloop 125-127 that is available between the DSLAM/VRAD 115-117 and thecustomer premises 110-111, and associates the selected loop 125-127 withthe selected DSLAM/VRAD port.

The example MLAC 130 of FIG. 1 may also be accessed using an interactivevoice response (IVR) and/or automated attendant system (not shown). Forexample, a technician 150 at the example customer premises 111 toinstall and/or troubleshoot the example CPE DSL modem 121 can telephonean IVR system implemented at the example MLAC 130 to request that thecustomer premises 111 be assigned a different DSLAM/VRAD port. Such portswap requests may occur to determine whether a problem associated withthe CPE DSL modem 121 at the customer premises 111 is caused by a badDSLAM/VRAD port. When such a DSLAM/VRAD port assignment change occurs,the example MLAC 130 and/or the example LFACS 135 flag the DSLAM/VRADport as potentially bad, thereby making the flagged DSLAM/VRAD portunavailable for use by and/or assignment to other customer premises110-112. In some circumstances, such a DSLAM/VRAD port swap may notresolve the issue(s) with the CPE DSL modem 121. Unless the exampletechnician 150 subsequently accesses the MLAC 130 to indicate that theoriginal DSLAM/VRAD port was not, in fact, bad, the original DSLAM/VRADport will remain flagged as potentially faulty by the example MLAC 130and the example LFACS 135. As such, some DSLAM/VRAD ports may remainunavailable for assignment and/or for use in diagnosing a serviceproblem even though they may, in fact, be operating correctly. Theexample technician 150 may likewise request that a loop 125-127associated with the customer premises 111 be changed and/or swapped.Swapped loops are likewise flagged as potentially bad and may becomeunavailable for use to provide services to another customer premises110-112 unless the technician 150 subsequently indicates that theswapped loop was, in fact, not faulty. In some instances, the diagnosticswaps of ports and/or loops may be more prevalent during field trialsand/or the deployment of new and/or emerging services.

The example technician 150 of FIG. 1 may, additionally or alternatively,interact with the example MLAC 130 via any type of wired and/or wirelesscommunication technology. For example, the technician 150 may use aportable computer (not shown) to access the example MLAC 130 to requestDSLAM/VRAD port and/or loop swaps.

The example MLAC 130 of FIG. 1 interacts with the example LFACS 135 toidentify which DSLAM/VRAD ports and/or loops are available forassignment to a particular customer premises 110-112. In response tosuch requests, the example LFACS 135 of FIG. 1 queries the exampleport/loop assignment database 140. When a DSLAM/VRAD port and/or loopassignment and/or swap is identified by the MLAC 130, the example LFACS135 of FIG. 1 updates the port/loop assignment database 140 andconfigures the corresponding DSLAM/VRAD 115-117 via any type of accessmanagement system 155.

To proactively monitor DSLAM/VRAD port utilization, the example accessnetwork 100 of FIG. 1 includes an availability analyzer 160. Based onDSLAM/VRAD port utilization information and/or loop utilizationinformation stored in the example port/loop assignment database 140, theexample availability analyzer 160 of FIG. 1 determines whethermaintenance should be performed for a particular DSLAM/VRAD 115-117.Periodically and/or aperiodically, the example availability analyzer 160queries the example LFACS 135 to obtain the number “A” of currentlyassigned ports, and the number “B” of ports that are flagged and/oridentified as bad and/or potentially bad for a presently consideredDSLAM/VRAD 115-117. The availability analyzer 160 also queries and/orobtains a desired number “N” of ports that are needed for pending and/orprojected service needs for the presently considered DSLAM/VRAD 115-117from any type of capacity-planning server, system and/or organization165. Based on the numbers A and N, the example availability analyzer 160of FIG. 1 determines whether maintenance is needed for the presentlyconsidered DSLAM/VRAD 115-117 to restore flagged ports and/or loops to acorrectly operation state. For some loops and/or ports, a servicetechnician may only need to test and verify that the port and/or loopwas, in fact, fully operation and simply change its status in theport/loop assignment database 140 via the LFACS 135. In othercircumstances, ports and/or loops may require repair and/or replacementin order to return them to an available state. The example availabilityanalyzer 160 of FIG. 1 also uses the numbers A, B and N to determinewhether the port capacity of a DSLAM/VRAD 115-117 and/or CO/RT/SAI needsto be upgraded. An example manner of implementing the exampleavailability analyzer 160 of FIG. 1 is described below in connectionwith FIG. 4. An example process that may be carried out to implement theexample availability analyzer 160 is described below in connection withFIGS. 5A and 5B.

By proactively monitoring port exhaustion for the example DSLAMs/VRADs115-117 of FIG. 1, the example availability analyzer 160 provides anumber of benefits to an operator of the example access network 100. Forexample, by proactively identifying DSLAMs/VRADs 115-117 that are inneed of maintenance and/or upgrades, the example availability analyzer160 can help ensure that enough ports are available to sell, promoteand/or otherwise provide new services to additional customers, and/or tofacilitate the timely and efficient resolution of reported and/oridentified problems. For example, if there are no remaining availableDSLAM/VRAD ports, the example technician 150 would be unable to requesta port swap as part of a troubleshooting and/or diagnostic process. Suchcircumstances may result in wasted technician time, lost revenue, adiminished perceived image and/or reputation, and/or decreased customersatisfaction.

When the example availability analyzer 160 of FIG. 1 identifies aparticular DSLAM/VRAD 115-117 as requiring maintenance to restore theDSLAM/VRAD 115-117 to a state having a sufficient number A of availableports and/or loops to support pending and/or projected service needs,the example availability analyzer 160 automatically generates and/orsubmits a maintenance ticket to any type of trouble ticket system 170.Such an automatically generated and/or submitted maintenance ticketrepresents preventative, prospective, forecasted and/or projectedmaintenance needs that should be performed in order to, for example,reduce the likelihood that a requested service cannot be installedand/or provisioned when requested by a subscriber and/or to reduce thelikelihood that a reported service problem cannot be resolved in atimely manner. In response to the submitted maintenance ticket, anappropriate service and/or maintenance technician can be dispatched toreturn as many flagged ports and/or loops associated with the DSLAM/VRAD115-117 to an operational state. If the number A of available ports isdetermined to be critically low relative to the number N of neededports, the example availability analyzer 160 sets, adjusts and/ormodifies a severity flag and/or priority value associated with themaintenance ticket to identify that maintenance for the DSLAM/VRAD15-117 is needed and/or required on an urgent basis. The number A may bedetermined to be critically low when, for example, the ratio A/N is lessthan a predefined threshold.

Based on a plurality of numbers {B1, B2, . . . } of bad and/orpotentially bad ports associated with respective DSLAMs/VRADs 115-117,the example availability analyzer 160 creates an ordered list of theDSLAMs/VRADs 115-117. The list of DSLAMs/VRADs 115-117 are ordered basedupon their respective number B of bad and/or potentially bad ports. Insome examples, only DSLAMs/VRADs 115-117 that have been identified ashaving an insufficient number A of available ports and/or loops areincluded in the ordered list. The list of ordered DSLAMs/VRADs 115-117may be presented and/or accessed by a maintenance organization 175 via,for example, a web-based graphical user interface (GUI) and/or aweb-based dashboard.

FIG. 2 illustrates an example maintenance report 200 that may begenerated by the example availability analyzer 160 to present an orderedlist of DSLAMs/VRADs 115-117. The example maintenance report 200 of FIG.2 includes a plurality of entries 205 for respective ones of a pluralityof DSLAMs/VRADs 115-117 that were analyzed by the example availabilityanalyzer 160 and determined to require maintenance. To identify aDSLAM/VRAD 115-117, each of the example entries 205 of FIG. 2 includesan identifier field 210. Each of the example identifier fields 210 ofFIG. 2 contains one or more values, letters and/or strings that uniquelyidentify a particular DSLAM/VRAD 115-117.

To store the number B of bad ports, each of the example entries 205 ofFIG. 2 includes a bad field 215. Each of the example bad fields 215 ofFIG. 2 contains a value that represents the number B of bad and/orpotentially bad ports associated with the DSLAM/VRAD 115-117 representedby the corresponding identifier field 210. The example entries 205 ofFIG. 2 are sorted based on values in the example bad fields 215 suchthat the DSLAM/VRAD 115-117 having the largest number B of bad and/orpotentially bad ports (that is, in most need of maintenance) appears atthe top of the example maintenance report 200 of FIG. 2.

To store the number A of available ports, each of the example entries205 of FIG. 2 includes an available field 220. Each of the exampleavailable fields 220 of FIG. 2 contains a value that represents thenumber A of available ports associated with the DSLAM/VRAD 115-117represented by the corresponding identifier field 210. To store thenumber N of needed ports, each of the example entries 205 of FIG. 2includes a needed field 225. Each of the example needed fields 225 ofFIG. 2 contains a value that represents the number N of available portsassociated with the DSLAM/VRAD 115-117 represented by the correspondingidentifier field 210.

To identify ports and/or loops that potentially require maintenance,each of the example entries 205 of FIG. 2 includes a port/loopidentifier field 230. Each of the example port/identifier fields 230 ofFIG. 2 contains one or more values and/or identifiers that representeach of the ports and/or loops associated with the DSLAM/VRAD 115-117represented by the corresponding identifier field 210 that are currentlyflagged as bad and/or potentially bad.

While an example maintenance report 200 that may be generated and/orpresented by the example availability analyzer 160 of FIG. 1 isillustrated in FIG. 2, the example maintenance report 200 may beimplemented using any number and/or type(s) of other and/or additionalentries, fields and/or data. Further, the entries, fields and/or dataillustrated in FIG. 2 may be combined, divided, re-arranged, eliminatedand/or implemented in any way. Further still, a maintenance report mayinclude entries, fields and/or data in addition to, or instead of, thoseillustrated in FIG. 2, and/or may include more than one of any or all ofthe illustrated entries, fields and/or data.

Returning to FIG. 1, as described below in connection with FIG. 5A, theexample availability analyzer 160 of FIG. 1 computes a capacity gap Gfor each analyzed DSLAM/VRAD 115-117. Based on a plurality of capacitygaps {G1, G2, . . . } associated with respective DSLAMs/VRADs 115-117,the example availability analyzer 160 creates another ordered list ofthe DSLAMs/VRADs 115-117. The additional list of DSLAMs/VRADs 115-117 isordered based upon their respective capacity gap G. In some examples,only DSLAMs/VRADs 115-117 that have been identified as needing acapacity upgrade are included in this second ordered list. The secondlist of ordered DSLAMs/VRADs 115-117 may be presented and/or accessed bya user (not shown) of the example capacity-planning server 165 via, forexample, a web-based GUI and/or a web-based dashboard.

FIG. 3 illustrates an example capacity-planning report 300 that may begenerated by the example availability analyzer 160 to represent thesecond ordered list of DSLAMs/VRADs 115-117. The examplecapacity-planning report 300 of FIG. 3 includes a plurality of entries305 for respective ones of a plurality of DSLAMs/VRADs 115-117 that wereanalyzed by the example availability analyzer 160 and determined torequire a capacity upgrade. To identify a DSLAM/VRAD 115-117, each ofthe example entries 305 of FIG. 3 includes an identifier field 310. Eachof the example identifier fields 310 of FIG. 3 contains one or morevalues, letters and/or strings that uniquely identify a particularDSLAM/VRAD 115-117.

To store a computed capacity gap G, each of the example entries 305 ofFIG. 3 includes a gap field 315. Each of the example gap fields 315 ofFIG. 3 contains a value that represents the gap between the pendingand/or projected needs of the DSLAM/VRAD 115-117 represented by thecorresponding identifier field 210 and the potential number of portsthat could be available at the DSLAM/VRAD 115-117 assuming maintenanceof the DSLAM/VRAD 115-117 is performed. The example entries 305 of FIG.3 are sorted based on the example values stored in the gap fields 315such that the DSLAM/VRAD 115-117 having the smallest capacity gap G(that is, in most need of a capacity upgrade) appears at the top of thecapacity-planning report 300.

To store the number A of available ports, each of the example entries305 of FIG. 3 includes an available field 320. Each of the exampleavailable fields 320 of FIG. 3 contains a value that represents thenumber A of available ports associated with the DSLAM/VRAD 115-117represented by the corresponding identifier field 310. To store thenumber B of bad ports, each of the example entries 305 of FIG. 3includes a bad field 325. Each of the example bad fields 325 of FIG. 3contains a value that represents the number B of bad and/or potentiallybad ports associated with the DSLAM/VRAD 115-117 represented by thecorresponding identifier field 310. To store the number N of neededports, each of the example entries 305 of FIG. 3 includes a needed field330. Each of the example needed fields 330 of FIG. 3 contains a valuethat represents the number N of available ports associated with theDSLAM/VRAD 115-117 represented by the corresponding identifier field310.

While an example capacity-planning report 300 that may be generatedand/or presented by the example availability analyzer 160 of FIG. 1 isillustrated in FIG. 3, the example capacity-planning report 300 may beimplemented using any number and/or type(s) of other and/or additionalentries, fields and/or data. Further, the entries, fields and/or dataillustrated in FIG. 3 may be combined, divided, re-arranged, eliminatedand/or implemented in any way. Further still, a capacity-planning reportmay include entries, fields and/or data in addition to, or instead of,those illustrated in FIG. 3, and/or may include more than one of any orall of the illustrated entries, fields and/or data.

Returning to FIG. 1, to manage repair and/or maintenance reports, theexample access network 100 of FIG. 1 includes the example trouble ticketsystem 170. The example trouble ticket system 170 of FIG. 1 implementsany API via which the example availability analyzer 160 can submit amaintenance ticket. The example trouble ticket system 170 also routes asubmitted maintenance ticket to a suitable repair, customer supportand/or technical support person for resolution, and tracks theresolution of trouble tickets.

While an example access network 100 has been illustrated in FIG. 1, oneor more of the interfaces, data structures, elements, processes and/ordevices illustrated in FIG. 1 may be combined, divided, re-arranged,omitted, eliminated and/or implemented in any other way. Further, theexample MLAC 130, the example LFACS 135, the example customer serviceserver 145, the example AMS 155, the example availability server 160,the example capacity-planning server 165 and/or the example troubleticket system 170 of FIG. 1 may be implemented by hardware, software,firmware and/or any combination of hardware, software and/or firmware.Thus, for example, any of the example MLAC 130, the example LFACS 135,the example customer service server 145, the example AMS 155, theexample availability server 160, the example capacity-planning server165 and/or the example trouble ticket system 170 may be implemented byone or more device(s), circuit(s), programmable processor(s),application specific integrated circuit(s) (ASIC(s)), programmable logicdevice(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)),etc. Further still, an access network may include interfaces, datastructures, elements, processes and/or devices instead of, or inaddition to, those illustrated in FIG. 1 and/or may include more thanone of any or all of the illustrated interfaces, data structures,elements, processes and/or devices.

FIG. 4 illustrates an example manner of implementing the exampleavailability analyzer 160 of FIG. 1. To interact with the example LFACS135 and/or the example capacity-planning server 165, the exampleavailability analyzer 160 of FIG. 4 includes any type of interfacemodule 405. An example interface module 405 is implemented in accordancewith any past, present and/or future standard, specification and/orrecommendation, such as the Institute of Electrical and ElectronicsEngineers (IEEE) 802.x family of standards for Ethernet. Additionally oralternatively, the example interface module 405 may implement any numberand/or type(s) of customized and/or specific interfaces implemented bythe example LFACS 135 and/or the example capacity-planning server 165.

To analyze the capacity of the example DSLAMs/VRADs 115-117, the exampleavailability analyzer 160 of FIG. 4 includes a data analysis module 410.The example data analysis module 410 of FIG. 1 queries, via the exampleinterface module 405, the example LFACS 135 to obtain the number “A” ofcurrently assigned ports, and the number “B” of ports that are flaggedand/or identified as bad and/or potentially bad for a presentlyconsidered DSLAM/VRAD 115-117. The example data analysis module 410 alsoqueries and/or obtains a desired number “N” of ports that are needed forpending and/or projected service needs for the presently consideredDSLAM/VRAD 115-117 from the capacity-planning server 165 via theinterface module 405. Based on the obtained numbers A and N, the exampledata analysis module 410 of FIG. 4 determines whether maintenance isneeded for the presently considered DSLAM/VRAD 115-117 to restoreflagged ports and/or loops to a correctly operation state. The exampledata analysis module 410 also uses the numbers A, B and N to determinewhether the port capacity of a DSLAM/VRAD 115-117 and/or CO/RT/SAI needsto be upgraded. An example process that may be carried out to implementthe data analysis module 410 is described below in connection with FIGS.5A and 5B.

To initiate DSLAM/VRAD port utilization analysis by the example dataanalysis module 410, the example availability analyzer 160 of FIG. 4includes any type of scheduler 415. Based on any number and/or type(s)of criteria, the example scheduler 415 of FIG. 4 periodically oraperiodically directs the data analysis module 410 to analyze one ormore of the example DSLAMs/VRADs 115-117. For example, the examplescheduler 415 could initiate port and/or loop analysis on a daily, aweekly and/or a monthly basis. Additionally and/or alternatively,operation of the example data analysis module 410 may be trigger by, forexample, a person associated with the example maintenance organization175 and/or the capacity-planning server 165.

To interact with the example trouble ticket system 170 of FIG. 1, theexample availability analyzer 160 of FIG. 4 includes a trouble ticketsubmitter 420. The example trouble ticket submitter 420 of FIG. 4generates and submits maintenance tickets against DSLAMs/VRADs 115-117that were identified by a data analysis module 410 as needing to havemaintenance performed. The example trouble ticket submitter 420 submitsa trouble ticket by, for example, accessing and/or utilizing an APIprovided and/or implemented by the example trouble ticket system 170. Insome examples, the trouble ticket submitter 420 accesses the troubleticket system 170 via the example interface module 405.

To generate maintenance and/or capacity-planning reports, the exampleavailability analyzer 160 of FIG. 4 includes a report generator 425.Based on a plurality of numbers {B1, B2, . . . } of bad and/orpotentially bad ports associated with respective DSLAMs/VRADs 115-117,the example report generator 425 of FIG. 4 creates a maintenance report,such as the example maintenance report 200 of FIG. 2. The example reportgenerator 425 arranges a list of DSLAMs/VRADs 115-117 within thegenerated maintenance report based upon their respective number B of badand/or potentially bad ports. In some examples, only DSLAMs/VRADs115-117 that have been identified by the example data analysis module410 as having an insufficient number A of available ports and/or loopsare included in the maintenance report. The maintenance report may bepresented and/or accessed by the example maintenance organization 175 ofFIG. 1 via, for example, a web-based GUI and/or a web-based dashboard.In some examples, the report generator 425 presents and/or provides themaintenance report to the maintenance organization 175 via the exampleinterface module 405.

Based on a plurality of capacity gaps {G1, G2, . . . } computed forrespective DSLAMs/VRADs 115-117, the example report generator 425 ofFIG. 4 creates a capacity-planning report, such as the examplecapacity-planning report 300 of FIG. 3. The example report generator 425arranges a list of DSLAMs/VRADs 115-117 within the generatedcapacity-planning report based upon their respective capacity gap Gvalues. In some examples, only DSLAMs/VRADs 115-117 that have beenidentified by the example data analysis module 410 as needing a capacityupgrade are included in the capacity-planning report. Thecapacity-planning report may be presented and/or accessed by a user (notshown) of the example capacity-planning server 165 via, for example, aweb-based GUI and/or a web-based dashboard. In some examples, the reportgenerator 425 presents and/or provides the capacity report to thecapacity-planning server 165 via the example interface module 405.

While an example manner of implementing the example availabilityanalyzer 160 of FIG. 1 has been illustrated in FIG. 4, one or more ofthe elements, processes, interfaces and/or devices illustrated in FIG. 4may be combined, divided, re-arranged, omitted, eliminated and/orimplemented in any other way. Further, the example interface module 405,the example data analysis module 410, the example scheduler 415, theexample trouble ticket submitter 420, the example report generator 425and/or, more generally, the example availability analyzer 160 of FIG. 4may be implemented by hardware, software, firmware and/or anycombination of hardware, software and/or firmware. Thus, for example,any or all of the example interface module 405, the example dataanalysis module 410, the example scheduler 415, the example troubleticket submitter 420, the example report generator 425 and/or, moregenerally, the example availability analyzer 160 may be implemented byone or more circuit(s), programmable processor(s), ASIC(s), PLD(s)and/or FPLD(s), etc. Further still, an availability analyzer may includeone or more elements, processes, interfaces and/or devices in additionto, or instead of, those illustrated in FIG. 4, and/or may include morethan one of any or all of the illustrated elements, processes,interfaces and devices.

FIGS. 5A and 5B collectively illustrate a flowchart representative of anexample process that may be carried out to implement the exampleavailability analyzer 160 of FIGS. 1 and 4. The example process of FIGS.5A and 5B may be carried out by a processor, a controller and/or anyother suitable processing device. For example, the example process ofFIGS. 5A and 5B may be embodied in coded instructions stored on anytangible computer-readable medium such as a flash memory, a compact disc(CD), a digital versatile disc (DVD), a floppy disk, a read-only memory(ROM), a random-access memory (RAM), a programmable ROM (PROM), anelectronically-programmable ROM (EPROM), and/or anelectronically-erasable PROM (EEPROM), an optical storage disk, anoptical storage device, magnetic storage disk, a magnetic storagedevice, and/or any other medium which can be used to carry or storeprogram code and/or instructions in the form of machine-accessibleinstructions or data structures, and which can be accessed by aprocessor, a general-purpose or special-purpose computer, or othermachine with a processor (e.g., the example processor platform P100discussed below in connection with FIG. 6). Combinations of the aboveare also included within the scope of computer-readable media.Machine-accessible instructions comprise, for example, instructionsand/or data that cause a processor, a general-purpose computer,special-purpose computer, or a special-purpose processing machine toimplement one or more particular processes. Alternatively, some or allof the example process of FIGS. 5A and 5B may be implemented using anycombination(s) of ASIC(s), PLD(s), FPLD(s), discrete logic, hardware,firmware, etc. Also, some or all of the example process of FIGS. 5A and5B may instead be implemented manually or as any combination of any ofthe foregoing techniques, for example, any combination of firmware,software, discrete logic and/or hardware. Further, many other methods ofimplementing the example operations of FIGS. 5A and 5B may be employed.For example, the order of execution of the blocks may be changed, and/orone or more of the blocks described may be changed, eliminated,sub-divided, or combined. Additionally, any or all of the exampleprocess of FIGS. 5A and 5B may be carried out sequentially and/orcarried out in parallel by, for example, separate processing threads,processors, devices, discrete logic, circuits, etc.

The example process of FIGS. 5A and 5B begins with the example dataanalysis module 410 of FIG. 4 obtaining from the example LFACS 135 viathe example interface module 405 the number A of available ports and/orloops associated with a presently considered DSLAM/VRAD 115-117 (block505). The data analysis module 410 obtains from the examplecapacity-planning server 165 via the example interface module 405 thenumber N of needed ports and/or loops for the presently consideredDSLAM/VRAD 115-117 (block 510). If a ratio of A and N (that is, A/N) isless than a first threshold (block 515), the data analysis module 410obtains from the example LFACS 135 the number B of bad and/orpotentially bad ports and/or loops associated with the presentlyconsidered DSLAM/VRAD 115-117 (block 520). The data analysis module 410tags or flags the presently considered DSLAM/VRAD 115-117 as needingmaintenance (block 525) and the example trouble ticket submitter 420 ofFIG. 4 generates and submits a maintenance ticket against the presentlyconsidered DSLAM/VRAD 115-117 (block 530).

The data analysis module 410 calculates the capacity gap G of thepresently considered DSLAM/VRAD 115-117 (block 535). An example capacitygap value G is computed using the following mathematical expression:G=(A+B)−N. If the computed capacity gap value G is less than a secondthreshold (block 540), the data analysis module 410 tags or flags thepresently considered DSLAM/VRAD 115-117 for a capacity upgrade (block545). In some examples, the first and second thresholds have the samevalue. If the computed capacity gap G is not less than the secondthreshold (block 540), control proceeds to block 550 without flaggingthe presently considered DSLAM/VRAD 115-117 for a capacity upgrade.

Returning to block 515, if the ratio A/N is not less than the firstthreshold (block 515), control proceeds to block 550 without flaggingthe presently considered DSLAM/VRAD 115-117 for maintenance and withoutflagging the presently considered DSLAM/VRAD 115-117 for a capacityupgrade.

At block 550, if there are more DSLAMs/VRADs to process (block 550),control returns to block 505 to process the next DSLAM/VRAD 115-117. Ifthere are no more DSLAMs/VRADs 115-117 to process (block 550), controlproceeds to block 555 of FIG. 5B.

The example report generator 425 of FIG. 4 sorts the DSLAMs/VRADs115-117 that were flagged by the data analysis module 410 formaintenance based on their associated numbers B or bad and/orpotentially bad ports (block 555 of FIG. 5B). Based on the ordered listof flagged DSLAMs/VRADs 115-117, the report generator 425 creates amaintenance report and/or web-based dashboard, such as the examplemaintenance report 200 of FIG. 2 (block 560).

If any DSLAMs/VRADs 115-117 have a critically low number A of availableports (block 565), the example trouble ticket submitter 420 escalatesand/or prioritizes maintenance of the DSLAM(s)/VRAD(s) 115-117 by, forexample, setting a priority value and/or severity flag associated with agenerated and/or submitted maintenance ticket to severe (block 570).

The example report generator 425 sorts the DSLAMs/VRADs 115-117 thatwere flagged by the data analysis module 410 for capacity upgrades(block 575). Based on the ordered list of flagged DSLAMs/VRADs 115-117,the report generator 425 creates a capacity-planning report and/orweb-based dashboard, such as the example capacity-planning report 300 ofFIG. 3 (block 580). Control then exits from the example process of FIGS.5A and 5B.

FIG. 6 is a schematic diagram of an example processor platform P100 thatmay be used and/or programmed to implement the example availabilityanalyzers 160 of FIGS. 1 and 4. For example, the processor platform P100can be implemented by one or more general-purpose processors, processorcores, microcontrollers, etc.

The processor platform P100 of the example of FIG. 6 includes at leastone general purpose programmable processor P105. The processor P105executes coded instructions P110 and/or P112 present in main memory ofthe processor P105 (e.g., within a RAM P115 and/or a ROM P120). Theprocessor P105 may be any type of processing unit, such as a processorcore, a processor and/or a microcontroller. The processor P105 mayexecute, among other things, the example process of FIGS. 5A and 5B toimplement the example methods and apparatus described herein.

The processor P105 is in communication with the main memory (including aROM P120 and/or the RAM P115) via a bus P125. The RAM P115 may beimplemented by DRAM, SDRAM, and/or any other type of RAM device, and ROMmay be implemented by flash memory and/or any other desired type ofmemory device. Access to the memory P115 and the memory P120 may becontrolled by a memory controller (not shown). One or both of theexample memories P115 and P120 may be used to implement the exampleport/loop assignment database 140 of FIG. 1.

The processor platform P100 also includes an interface circuit P130. Theinterface circuit P130 may be implemented by any type of interfacestandard, such as an external memory interface, serial port,general-purpose input/output, etc. One or more input devices P135 andone or more output devices P140 are connected to the interface circuitP130. The input devices P135 and/or output devices P140 may be used to,for example, implement the interface module 405 of FIG. 4.

Although certain example methods, apparatus and articles of manufacturehave been described herein, the scope of coverage of this patent is notlimited thereto. On the contrary, this patent covers all methods,apparatus and articles of manufacture fairly falling within the scope ofthe appended claims either literally or under the doctrine ofequivalents.

What is claimed is:
 1. A method to verify a port, comprising:identifying a first value representing a number of unassigned portsassociated with a first digital subscriber line access multiplexer;identifying a number of ports of the first digital subscriber lineaccess multiplexer associated with a status of potentially bad inresponse to a port swap of the first digital subscriber line accessmultiplexer at a first time; adjusting the first value based on thenumber of potentially bad ports; identifying a second value representinga projected number of ports associated with the first digital subscriberline access multiplexer needed to satisfy a pending service request at asecond time; verifying whether the number of ports associated with thestatus of potentially bad are operating correctly at the second time;and submitting a preventative maintenance trouble ticket for the firstdigital subscriber line access multiplexer based on the adjusted firstvalue and the second value.
 2. A method as defined in claim 1, whereinsubmitting the preventative maintenance trouble ticket further comprisescomparing a ratio of the adjusted first value and the second value.
 3. Amethod as defined in claim 2, further comprising adjusting a severitythreshold of the preventative maintenance trouble ticket when the ratioof the adjusted first value and the second value is less than athreshold.
 4. A method as defined in claim 2, further comprisingestablishing a maintenance repair order for the first digital subscriberline access multiplexer and a plurality of other digital subscriber lineaccess multiplexers based on the ratio.
 5. A method as defined in claim1, further comprising changing the status of the number of portsassociated with the status of potentially bad to a status of operationalwhen operating correctly at the second time.
 6. A method as defined inclaim 1, further comprising changing the status of the number of portsassociated with the status of potentially bad to a status of bad whennot operating correctly at the second time.
 7. A method as defined inclaim 1, wherein the first value represents the number of unassignedports associated with the first digital subscriber line accessmultiplexer and a number of loops associated with the first digitalsubscriber line access multiplexer.
 8. A method as defined in claim 1,wherein the first digital subscriber line access multiplexer comprises avideo ready access device.
 9. An apparatus comprising: a memory storingmachine readable instructions; and a processor to execute theinstructions to: identify a first value representing a number ofunassigned ports associated with a first digital subscriber line accessmultiplexer; identify a number of ports of the first digital subscriberline access multiplexer associated with a status of potentially bad inresponse to a port swap of the first digital subscriber line accessmultiplexer at a first time; adjust the first value based on the numberof potentially bad ports; identify a second value representing aprojected number of ports associated with the first digital subscriberline access multiplexer needed to satisfy a pending service request at asecond time; verify whether the number of ports associated with thestatus of potentially bad are operating correctly at the second time;and submit a preventative maintenance trouble ticket for the firstdigital subscriber line access multiplexer based on the adjusted firstvalue and the second value.
 10. An apparatus as defined in claim 9,further comprising a capacity planning server to compare a ratio of theadjusted first value and the second value.
 11. An apparatus as definedin claim 10, wherein the trouble ticket submitter is to adjust aseverity threshold of the preventative maintenance trouble ticket whenthe ratio of the adjusted first value and the second value is less thana threshold.
 12. An apparatus as defined in claim 10, further comprisinga scheduler to establish a maintenance repair order for the firstdigital subscriber line access multiplexer and a plurality of otherdigital subscriber line access multiplexers based on the ratio.
 13. Anapparatus as defined in claim 9, further comprising an availabilityanalyzer to change the status of the number of ports associated with thestatus of potentially bad to a status of operational when operatingcorrectly at the second time.
 14. An apparatus as defined in claim 9,further comprising an availability analyzer to change the status of thenumber of ports associated with the status of potentially bad to astatus of bad when not operating correctly at the second time.
 15. Anapparatus as defined in claim 9, wherein the first value represents thenumber of unassigned ports associated with the first digital subscriberline access multiplexer and a number of loops associated with the firstdigital subscriber line access multiplexer.
 16. An apparatus as definedin claim 9, wherein the first digital subscriber line access multiplexercomprises a video ready access device.
 17. A tangible machine readablestorage medium comprising instructions which, when executed, cause amachine to perform operations comprising: identifying a first valuerepresenting a number of unassigned ports associated with a firstdigital subscriber line access multiplexer; identifying a number ofports of the first digital subscriber line access multiplexer associatedwith a status of potentially bad in response to a port swap of the firstdigital subscriber line access multiplexer at a first time; adjustingthe first value based on the number of potentially bad ports;identifying a second value representing a projected number of portsassociated with the first digital subscriber line access multiplexerneeded to satisfy a pending service request at a second time; verifyingwhether the number of ports associated with the status of potentiallybad are operating correctly at the second time; and submitting apreventative maintenance trouble ticket for the first digital subscriberline access multiplexer based on the adjusted first value and the secondvalue.
 18. A tangible machine readable storage medium as defined inclaim 17, wherein the instructions, when executed, cause the machine tocompare a ratio of the adjusted first value and the second value.
 19. Atangible machine readable storage medium as defined in claim 18, whereinthe instructions, when executed, cause the machine to adjust a severitythreshold of the preventative maintenance trouble ticket when the ratioof the adjusted first value and the second value is less than athreshold.
 20. A tangible machine readable storage medium as defined inclaim 18, wherein the instructions, when executed, cause the machine toestablish a maintenance repair order for the first digital subscriberline access multiplexer and a plurality of other digital subscriber lineaccess multiplexers based on the ratio.